Version 5.0 Jun. 15th, 1992 ************** * 2. DTCs * ************** Different versions History -------------------------- Version 1.0 : Created in 1990. Version 2.0 : Available June 91, updated with DTC Release 10.5 information. Version 3.0 : Available Oct. 91, updated with : - New Competitive information (Mainly on DEC new offering) - DTC Performance in HP-UX environments now available - Q/A on MUX/DTC transparency in HP9000 environments updated. Version 4.0 : Available December 91, updated with DTC Release 12.0 information. Version 5.0 : Available June 92, updated with: - HP OpenView DTC Manager release 12.1 - HP OpenView DTC Entry-Level Manager/UX 2.0 - New Competitive information - New DTC16 pricing /////////////////////////////////////////////// * * * A. NEW SINCE LAST VERSION * * * /////////////////////////////////////////////// ************************************** * June 92 DTC releases at a glance * ************************************** "A New Step Toward Making The DTC The Clear Terminal Server Of Choice For HP-UX" . Product name and P/N: HP Datacommunication and Terminal Controller (DTC) DTC16, P/N 2340A; DTC48, P/N 2345A . Description: Dual protocol multivendor communication server optimized for the HP environment . Target market: Multiuser standalone or multiple LAN-attached HP systems in HP and/or multivendor environment. This new release is most particularly intended for standalone HP 9000 series 800 customers (system expansion and decentralized terminal connectivity). . Major enhancements: - HP 9000 Mux-compatible interface - 20% performance improvement under HP 9000 based management - Large HP 9000 configurations support - Enhanced support of 3rd-party applications on MPE/iX - PC software installability enhancements With the latest revision of the DTC software, HP takes another important step toward making the DTC the clear server of choice for HP- UX: - HP 9000 Mux-compatible interface: allows customers/VARs to use most applications designed for Muxes with the DTC without modifications. This feature is superior in functionality and provides better system integration than solutions available with third-parties terminal server implementations. (Please refer to the "DTC now surpasses competition with HP 9000 nailed ports" article in this Computer News issue) - Performance improvement under HP 9000-based management: 20% overall system/DTC performance improvement compared to previous release. - Large HP 9000 configurations support: extended configuration capabilities are provided to support large scale OLTP for the HP 9000. These enhancements are available when the DTC is managed from the HP 9000 or the HP OpenView DTC Manager Workstation. In addition, HP continues the evolution of the DTC as a means to increase customer's operational efficiency through enhanced support of third-party applications on MPE/iX for PAD and Telnet users. Last but not least, network managers are provided with significant PC software installability enhancements that virtually eliminates the risk of errors and increases the ease of use. Features and Benefits HP 9000 Mux-compatible interface . DTC Telnet extension utilities (including "nailed/dedicated ports"): Access to DTC-connected devices Most applications designed to via standard Unix device file access multiplexers can use I/O terminal server technology without modifications DTC port identification (via Provides identity checking of DTC IP address or DTC board/port devices, thus allowing security identifiers) checks and printing of documents on appropriate DTC printer Performance improvements . 20% performance improvements Ability to support more in host-based configurations users/printers per system and DTC . Telnet/TCP/IP tuning for output intensive applications Large HP 9000 configurations . Extended terminal configuration Allows high-end systems to support (up to 150 DTCs) achieve their full user capacity potential . Tools for large number of users Provides configuration, (PC-based only) management and troubleshooting functions that can be used on a group of DTCs, thus making configuration of multiple devices faster and easier . Find port tool Provides physical location of a (PC-based only) DTC port Enhanced applications support on the HP 3000 . Telnet/iX user block-mode Enlarges the number of and type-ahead support applications supported through Telnet/iX products (e.g. Cognos "Quick" product) . Padsup/iX application Enlarges the number of type-ahead support applications supported through DTC/X.25 PAD Support (e.g. Cognos "Quick" product) . Enable/disable user log-on, Enhances application support in enable/disable ENQ/ACK protocol DTC back-to-back configurations Ensures MPE-V migration PC software installability . PC installer using expert Reduces installation time of technology the PC software and dramatically reduces the risk of installation errors. Requirements for installed base . HP DTC16 hardware - no specific requirements . HP DTC48 hardware - DTC48 with date code less than 3110 requires a memory extension (HP2348A) to take advantage of the new functionalities (see "New HP DTC48 upgrade kit" in the June 1st, 1991 issue of Computer News) . HP OpenView DTC Manager software - must be updated to the 12.1 release (see related article in this issue of Computer News) . HP OpenView DTC Entry-Level Manager/UX - must be updated to the 2.0 release (see related article in this issue of Computer News) . MPE iX Fundamental Operating System (FOS) - the HP 3000 Series 900- specific enhancements are supported with MPE iX release 2.2 or later . HP-UX Operating system - the HP 9000-specific enhancements are supported with HP-UX release 8.0 or later. Note that the DTC Telnet extension utilities will be available with the next release of HP-UX but are currently available through standard electronic delivery. NOTE: We most particularly recommend you to read the "Product description" and "Q&A" sections for more information on the DTC functionality enhancements provided by the new releases. For information related to the network management, please refer to the DTCMgr section of the Network Hotline. ======================================================================= /////////////////////////////////////////////// * * * B. PRODUCT DESCRIPTION * * * /////////////////////////////////////////////// *****CURRENT DTC RELEASES DISTRIBUTED***** HP OpenView DTC Manager 12.0 HP OpenView DTC Entry-Level Manager/UX 2.0 ****************************************** The Datacommunications and Terminal Controller (DTC) is HP's strategic platform for terminal and datacommunications access in networked multivendor system envi ronments (HP and other vendors systems). The DTC is a modular and flexible LAN- based controller which provides asynchronous connectivity and PAD support for local and remote terminals* and printers. The DTC provides location-independent end-user access to HP and non-HP systems, implementing both an optimized protocol for on-line transaction processing applications and the industry- standard Telnet-TCP/IP protocol suite. * (Footnote: PCs with appropriate terminal emulation software are supported as terminals) The DTC also implements Telnet services for the HP 3000 Series 900, and X.25 system-to-system networking for the HP 3000 Series 900. Even though this hotline concentrates on the terminal and printer connectivity features of the DTC, you will find information about the above capabilities; however we recommend to refer to the appropriate Network Hotlines ("ARPA/iX" and "DTCX25") and Data Sheets in the HP Networking Communications Specification Guide (P/N 5091-1303E) for more detailed technical information on Telnet and X.25 networking for the HP 3000 Series 900. The DTC solutions consists of: A scalable family of multivendor terminal servers: DTC16: provides up to 16 asynchronous connections 1 X.25 link supporting up to 32 virtual circuits at speeds of up to 19.2 kbps DTC48: provides up to 48 asynchronous connections 3 X.25 links supporting up to 256 virtual circuits each at speeds of up to 64 kbps. one Telnet Access card with 40 Telnet connections to HP 3000 Series 900 systems. A scalable family of Network Management products, depending on the system environment and the level of functionality required: Host-based management software based on HP systems for HP standalone environments (HP OpenView DTC Entry-level Manager/UX for HP9000 Series 800 systems and NMMGR and TERMDSM utilities for HP 3000 Series 900) Host-based management is also available when X.25 access to an HP 3000 Series 900 single system is required. PC-based management software for multi-system environments, or when X.25 access or when Telnet access via the DTC is desired (HP OpenView DTC Manager) The host-based management solution is designed for environments where a single operator manages both the system and the network associated. The PC-based management solution is designed for more complex networks with multiple systems including diverse equipment such as terminal servers, PADs, switches, bridges and hubs. In this environment the PC- based solution is a management station integrating all management elements (such as HP OpenView DTC manager, Switch/PAD manager, Hub manager, Bridge manager, Sysman) under the control of one operator. It also offers a broader set of features for DTC management, including dynamic configuration and an easy-to-use graphical interface integrated under HP OpenView. FEATURES AND BENEFITS --------------------- Features Benefits o Dual protocol Communication o Combined benefits of industry Server (HP 3000 Series 900 standards and OLTP optimized and Telnet/TCP/IP protocols) protocols. Consistent access to applications running on HP and non-HP systems o Support of Industry o Multivendor connectivity allows standard Telnet (TCP/IP) investment protection through the ability to share resources o Interoperability test package o Assurance of multivendor for Field certification of connectivity guarantees investment Multivendor networks protection o Access from DTC to remote o Support of remote LAN system over IP networks (*) configurations increases network (interconnected via routers) flexibility,capacity to grow and security while decreasing costs o Homogeneous system access for o Provides additional network local and remote (extended LANS flexibility and end-user and X.25) end-users productivity through location-independent access o Multi-session, Network o Increase end-user productivity symbolic names resolution and ease of use (via DNS), friendly user interface o HP OpenView Based DTC o Choice of Host or PC-based DTC management management --depending on environment-- contributes to optimized operating and equipment costs through the ability to manage multiple devices from one location (PADs, switches, DTCs, bridges and hubs) o Compatibility with existing o Investment protection DTC16 and DTC48 hardware (**) o TIO performance data from o Eases configuration/tuning choices Performance Hotline available when sizing HP9000 with DTC and Mux connections (*) Access to HP 3000 Series 900 through IP routers is provided through the use of the "Telnet Services for the HP 3000 Series 900". (**) DTC48 with datecode less than 3110 require an hardware upgrade For DTC Management specifics, please refer to the DTC Manager section in this Network Hotline. DTC16 and DTC48 PLATFORMS COMPARISON ------------------------------------ Hardware platform DTC16 | DTC48 Number of slots 3 | 6 (slot 3 dedicated to X.25) | (slot 0 must be Async) Asynchronous connectivity Max number of cards 2 | 6 RS-232 Modem 6 ports - 25 pins | 6 ports - 25 pins RS-232 Direct 8 ports - 25 pins | 8 ports - 3 pins RS-422 Direct Not available | 8 ports - 5 pins Data transfer rates 300, 1200, 2400, 4800, 9600 and 19200 bps Speed sensing yes | yes Parity sensing yes | yes Maximum number 5 | 5 of sessions/port | Maximum number 48 | 128 of sessions/DTC | LAN connectivity | ThinLAN yes | yes ThickLAN yes | yes Ethertwist yes | yes (AUI + Ethert. MAU required) | Broadband Ext. adapter required | Ext. adapter required FDDI Ext. adapter required | Ext. adapter required X.25 PAD connectivity | Max number of cards 1 | 3 Number of VCs/card 32 | 256 Interfaces/speed RS-232/19.2kbps | RS-232/19.2kbps | V.35/64kbps | V.36/64kbps | RS-422/64kbps PAD supported 128,256, | 128,256, packet length 512 bytes | 512 bytes | Telnet Access Card | (required for Telnet | Services on HP 3000 | Series 900) | Max number of cards N/A | 1 Max number of | sessions/card N/A | 40 | Access to systems via DNS (Domain Name Server) via their names via NS addressing via IP addressing Note: It is not possible to mix X.25 Network Access cards and Telnet Access Cards in one DTC. A dedicated server is also available (P/N 2344A) for end-users requiring more Telnet sessions to the HP 3000 Series Series 900 (80 sessions max). It is also known as HP ARPA Telnet Express. For more information, please refer to the "ARPA/iX" Hotline). CONNECTIVITY MATRIX ------------------- The Multivendor DTC provides the following end-user connectivity, based on a source/destination approach : Destination system +-----------+----------+----------+-----------+ | | | | | | HP 3000 | HP 9000 | ARPA | non-ARPA | | Series | Series | non-HP | HP or | | 900 | 300/400 | Host | non-HP | | | /800 | | Host | +- +-----------+----------+----------+-----------+ | Local | | | | | | | T/P | T/P | T | T/P | | +-----------+----------+----------+-----------+ end- | Remote | | | | | user | (X.25/PAD) | T/P | T/P | T | T | access | +-----------+----------+----------+-----------+ through | Bridges | | | | | | | T/P | T/P | T | T/P | | +-----------+----------+----------+-----------+ | Routers | | | | | | | T (1) | T/P | T | T/P | +- +-----------+----------+----------+-----------+ ARPA system | | DTC not | DTC not | | device (*) | YES (1) | involved | involved | YES | +-----------+----------+----------+-----------+ (*) refers to any device directly connected to an ARPA system, or a workstation ( PC or X-Terminals ) using the ARPA services. T: Terminal or PC in terminal emulation mode P: Printers (1) Access is done using Telnet services for the HP3000 Series 900 PROTOCOLS SUPPORTED ------------------- The DTC is a dual protocol multivendor terminal server. It combines the HP OLTP optimized protocol ( named "AFCP" ) with the de-facto standard Telnet/TCP/IP protocol suite. Each local or remote end-user can address the systems mentioned in the previous matrix using either AFCP or Telnet. The DTC will determine which protocol has to be used to provide the service. o AFCP/ADCP ( HP High-Performance OLTP Protocol ) o Telnet/TCP/IP : The DTC is based on the following standards: Telnet : MIL-STD 1782, RFC 854, 855, 856, 857, 859, 860, 1123 TCP : MIL-STD 1778, RFC 793, 813, 879, 964, 1122 IP : MIL-STD 1777, RFC 791, 815, 816, 879, 950, 963, 1122 ICMP : RFC-792, 1122 ARP : RFC-826 DNS : RFC-1034, 1035, 1123 o CCITT_84 X.25 o PAD Support: Compliant with CCITT_80 and CCITT_84 X.3 and X.29 INTEROPERABILITY TESTS COMPLETE AT PRODUCT INTRODUCTION ------------------------------------------------------- In order to demonstrate DTC's ability to talk with all HP systems, as well as other non-HP systems based on standards, the DTC has been tested with different systems. The systems mentioned within this list are already supported: Access to HP 3000 Series 900 ---------------------------- o HP 3000 Series 900 with: - MPE/iX 2.1 or later Access to systems implementing the Telnet/TCP/IP protocol suite --------------------------------------------------------------- o HP 3000 series 900 with: - HP ARPA Telnet Access release 10.5 or later, or - HP ARPA Telnet Express release 10.5 or later - MPE/iX 2.1 or later o HP 9000 Series 300/400/800 with: - HP-UX Release 7.0 or later - ARPA Services/9000 o HP 1000 Series with: - RTE-A Release 5.2 or later - ARPA Services/1000 o HP APOLLO Series with: - DOMAIN - ARPA Services o DEC VAX System with: - VMS Release 5.4 - NS VAX 2.2 o DEC VAX System with: - VMS Release 5.4 - WIN/VX 5.1 o SUN SparcServer with: - SUN-OS release 4.1 The list of tested systems is constantly growing, refer to the local Response Center to get an up-to-date list of tested configurations. If your configuration is not on this list, HP can provide a way to test it through the use of a "Multivendor Test Package" (availability since Sept. 91). DTC TELNET EXTENSION UTILITIES FOR HP-UX ---------------------------------------- Description: GND provides new competitive features for the DTC with HP9000 systems that no 3rd party terminal server can offer. The new DTC Telnet Extension Utilities for HP-UX and the DTC provide interface and functionality compatible with those of HP9000 system multiplexers. The DTC Telnet Extension Utilities go well beyond the competition offerings by providing the extended features, system integration, and lowest host-CPU overhead that only a single-vendor solution can deliver. These utilities are designed for LAN-based HP9000 using either the DTC16 or DTC48 (HP 2340A or HP 2345A) for terminal/printers/device connectivity. With these new HP-UX utilities for the DTC, customers can use existing HP-UX applications designed to be used with multiplexers over LANs and benefit from using the terminal server technology. These utilities can be used when the DTC is managed by the host or by a dedicated HP OpenView PC. These utilities allows any HP9000 to route spooler output to DTC-connected printers. In addition they provide features compatible with those of multiplexers : programmatic access to DTC devices via standard HP-UX system-calls and pseudo-terminal interface . All DTC devices are seen as locally attached to the system. As of today (June 1992), there are two utilities available: o "DTC Device File Access": provides system interface for nailed/dedicated devices ( host access to DTC-connected devices via standard UNIX device file i/o ). o "DTC Port Identification": provides system interface for identification of DTC-attached device. Benefits: By using the two utilities listed above, customers will get the following benefits: o Investment protection as HP-UX applications can use the terminal server technology, without loss of functionality. Now, most HP9000 applications can use the DTC without any modification. o Superior HP-system integration as DTC allows security checking, printing of documents on appropriate DTC printer, easy on-line diagnostics capabilities (e.g. identification of user device for operator log-out). Product Structure: The DTC Telnet Extension Utilities will be part of the ARPA software of the next general release of HP-UX (9.0). Prior to the availability of this release, these utilities can be obtained directly via UNIX mail: send a UNIX mail message to ddfa@hpnmcnt.cup.hp.com, and you will receive the appropriate file set including the DTC utilities and electronic documentation. Features & Benefits: o Transparent Port identification compatible with mux via Telnet logon ->Ensures application portability o Printer/device sharing capability directly via DTC (Multi-session capability of DTC) ->Avoids duplication of expensive resources o Any configuration change can be made without restarting all appplication (e.g. swaping device ports, changing port configuration) ->Increases system availability, avoids application shutdown o Support of status-request printers ->Optimizes use of HP Laser printers o Support of local DTC devices as well as remote via X.25 PAD devices ->Allows local-independent access from applications o Port identification via Standard Telnet ->Avoids use of other network protocols (Rlogin or others) ->Ensures lowest host-CPU overhead (No specific protocol added) o Automatic Ascii/Binary negotiation between DTC & HP9000 ->Simplifies configuration, avoiding to care about specific line behaviors o HP-UX compliant problems logging (SYSLOG) ->Allows system-integrated diagnostics: Only one source of problems tracking o No limitations in number of nailed devices (limitation is HP9000 maximum number of ptys) ->Solution available from low-end to high-end configurations Note: About previously available solution for DTC printers support: The solution that was available before these DTC Telnet Extension Utilities for HP-UX was based on the "DTC Device Access/ARPA" product (P/N D2355A options #AA1, #AA0, #AAH). The new utilities replace this product which is now discontinuated, but will continue to be supported during 1992 and H1 1993. These new utilities provide more features, are easier to use and are delivered bundled with the HP-UX operating system, thus easiing the ordering of a DTC & HP9000 configuration. GND's recommendation is to move to the new utilities for existing installations using the DTC Device Access/ARPA product, as these utilities will continue to be enhanced in the future. In terms of migration, the main difference between both generations of DTC software is the way to do programmatic access to DTC devices: * DTC Device Access/ARPA previous solution used a specific routines library. * DTC Telnet Extension Utilities for HP-UX use the standard system i/o HP-UX routines. Pre-requisites: These utilities are supported on all HP9000 platforms (Series 300/400/700 and 800), with HP-UX release 8.0 or later. They require the ARPA services on the HP9000 target system. All the above is available in both standalone system environments (using HP OpenView DTC Entry-Level Manager/UX release 2.0 running on an HP9000 Series 800) and multiple systems environments (using HP OpenView DTC Manager release 12.1 running on an HP OpenView DOS workstation). ===================================================================== ///////////////////////////////////////////////// * * * C. SALES INFORMATION * * * /////////////////////////////////////////////// COMPETITITIVE ANALYSIS ---------------------- The following competitive analysis compare the DTC to other non-HP solutions in the three following environments: 1- HP9000 HP-UX Standalone environment 2- HP3000 MPE/iX Standalone environment 3- HP Multiple-systems environment For each environment, we will list what are HP's DTC strengths and weaknesses versus other solutions. Then we will list the today price- list of a few non-HP terminal servers. 1- HP9000 HP-UX Standalone environment ------------------------------------ Environment description: one LAN-based HP9000 system where the network & device management is done by the system manager himself/herself. What is HP's DTC Competition?: The competition depends on the country, but overall we can list 4 main product families: XYPLEX servers, XYLOGICS servers, DATABILITY servers & SPIDER servers. HP's DTC Strengths: o Superior Performance on the system-side with lower host-CPU overhead due to the usage of the Telnet protocol (Please refer to the performance part of this hotline for more detailed information) o Superior system integration with the "DTC Telnet Extension Utilities" available today which provides additional services to the DTC & HP9000 (Please refer to this hotline for more detailed information regarding these DTC utilities) o Features which are available for both local and remote via X.25 PADs workstations o Ability to support 16-bits applications for the Asia/Pacific region HP's DTC has been tested and is supported in such environments. o Evolution of enhancements & features on a bi-annual basis, thus giving customers an insurance to get future DTC features available with DTC management software releases. These strengths contribute to position the DTC as the terminal server solution which ensures the best transparency of networks. This transparency gives customers greater investment protection as HP-UX applications that have been designed for multiplexers can be used with terminal server technology without loss of functionality. HP's DTC areas of weaknesses: As of today, the DTC unlike some of it's competitors doesn't provide the following features: o No support of Centronics-parallel ports o No support of SNMP, SLIP, Rlogin protocols o No support of the "KERBEROS" security user-authentication mechanism o No support of the Netware SPX/IPX protocol enabling Networked-PCs to share terminal server printers between the HP9000 system and the LAN-based PCs 2- HP3000 MPE/iX Standalone environment ------------------------------------ Environment description: one HP3000 MPE/iX without any other system connected on the network. What is HP's DTC competition?: Unless using a Telnet/TCP/IP terminal server and the ARPA services/iX, there is no solution other than the DTC. When using the Telnet/iX products with any Telnet/TCP/IP terminal server, the following restrictions will apply: o No printer support o Applications with HP-block-mode/Binary-mode behaviours are not supported o No nailed-devices capabilities (neither programmatic access) 3- HP Multiple-systems environment ------------------------------- Environment description : Multiple HP systems with at least one HP3000 MPE/iX system and other HP9000 HP-UX, HP1000 and non-HP systems. Who is HP's DTC competition: in this environment, the competition is either terminal server solution or data-switch solution. However general trend is to move from the data-switch solution to the terminal server solution (even if some solutions, such as the Ungermann-Bass solution Acces/one looks sometimes like a LAN data-switch). These terminal servers often support multiple protocols to provide access to ARPA, DEC and other systems in basic or complex network environments (including bridges, routers). In such environments, the network management task is done at a different level than the system management. Morever, the network & system management tasks are done by different entities of the company's IT department. Here, we find the following products: DECservers, Datability, Xyplex, Xylogics, 3COM, UB, Cisco, Spider, SCANET, etc.. HP's DTC Strengths: o Sharing of resource between multiple HP systems (either MPE/iX, HP-UX or RTE). No other 3rd-party solutions can provide system access and printer sharing for both local & remote via X.25 PADs devices. o Support of MPE/iX block-mode (including Vplus) terminals, VT220 terminals or RTE block-mode terminals: with HP's DTC, a single terminal can run all kinds of applications on different hosts and get the best of each individual system. o Supported multivendor connectivity: HP not only supports the DTC with non-HP systems, but also provides the tools to qualify/test and validate the usage of DTC with a non-HP system not already tested. o Ease of use: HP's DTC user interface is simple and robust. It doesn't require any user training nor special instructions unlike other products which provide a very complex command langage with more than 100 parameters..... HP's DTC is used to connect users to applications, that's all, end-users doen't have to deal with parameters! o Superior supportability : avoiding users to directly call the network manager when the connection to an application just failed. Users can ask DTC to diagnose if there is any problem on the network before calling some on-line service. HP's DTC Weaknesses: o No LAT protocol support: for accessing VAX/VMS systems on the local LAN This weaknesses "seems" less important, now that DEC provides it's own version of the Telnet service for VMS. Also, LAT not being routable, supporting LAT doesn't solve the problem of accessing remote systems via extended LAN configurations. o No Token-ring interface. The requirement for support of Token-ring directly on the DTC is currently being investigated. o No Telnet3270 support: Today only a few terminal servers also support the TN3270 protocol. Don't forget that this solution to access IBM systems requires software running on the IBM host, therefore adding important protocol overhead. GND is currenlty investigating the requirement for IBM system connectivity, and a status in this area will be done in the next release of this network hotline. o No support of SNMP, SLIP, Rlogin protocols o No support of the "KERBEROS" security user-authentication mechanism o No support of the Netware SPX/IPX protocol enabling Networked-PCs to share terminal server printers between the HP9000 system and the LAN- based PCs 4- Up-to-date Competitive Pricing ------------------------------ Price per port analysis includes hw price, without sw required for terminal server download or network management and without price of additional cables required to connect from box to patch-panel. Prices are US $ list-prices. Company Product Features Price/port ----------------------------------------------------------------------- DEC DEC700-8 LAT & Telnet -modem $375 DEC700-16 LAT & Telnet -RJ45 $238 DEC90L+ LAT, with power-bloc $181 DEC90TL LAT & Telnet, power-bloc $219 DEC250 LAT Printers server $704 XYPLEX MAX1600 LAT, Telnet, TN3270 $200 3COM CS2500 LAT, Telnet, TN3270 $280 requires boot server CS2600 LAT, Telnet & TN3270 $330 with floppy drive XYLOGICS m ELS 8 LAT & Telnet & conversion $287 m ELS 16 LAT & Telnet & conversion $175 m XL 8 LAT & Telnet $237 m XL 16 LAT & telnet $156 ANNEX III LAT & Telnet & conversion $109 EMULEX P4000 LAT & Telnet $172 DATABILITY VCP200 Lat & Telnet & conversion $250 VCP300 Lat & Telnet & conversion $187 VCP1000 Lat & Telnet & conversion $134 EQUINOX ELS-48 Lat & Telnet $163 DOWTY SCANET6 LAT, Telnet, OSI $263 Please forward any specific inquiry about terminal server market to the Network Sales Center who will forward your request to GND. NEW PRICING FOR DTC16 --------------------- With the latest release of the DTC software and associated network management, HP provides a competitive terminal server especially in terms of system integration and application transparency. To capitalize on this position, and make the DTC the clear server of choice for HP9000 terminal connect, we are cutting the price of the DTC16 by about 20% with a 6 months promotion which put it in the price range of the competition. This, promotion available worldwide by July 1st, 1992 is applicable when a fully loaded (two asynchronous cards) DTC16 is purchased with one or several HP3000 or HP9000 systems. The promotion reference is: 2.655 for US and ICON 078/92 for Europe Customers MUST purchase one of the following system products and is eligible for a quantity of DTC16 (2340A) in the range specified within the following table: Model Mini Maxi Number DTC16 DTC16 HP9000/807 HP3000/917LX 1 2 HP9000/817 HP3000/927LX 1 3 HP9000/827 HP3000/937LX/937 1 6 HP9000/837 HP3000/947LX/947 1 6 HP9000/847 HP3000/957LX/957 1 6 HP9000/857 1 9 HP9000/867 HP3000/967 1 9 HP9000/877 HP3000/977 1 12 HP9000/887 HP3000/987 1 12 HP9000/897 HP3000/990 1 12 HP9000/890/xxx HP3000/992/xxx 1 12 The detailled prices with the promotion discount are as follow: P/N Description US list price discounted US price ----------------------------------------------------------------------- 2340A DTC16 $ 2020 $ 1640 2340A opt #640 ThickLan & 6 modem RS232 ports $ 2340 $ 1895 2340A opt #641 AUI use & 6 modem RS232 ports $ 1870 $ 1515 2340A opt #642 ThinLan & 6 modem RS232 ports $ 1920 $ 1555 2340A opt #650 6 additional modem RS232 ports $ 1410 $ 1140 2340A opt #840 ThickLan & 8 direct RS232 ports $ 2340 $ 1895 2340A opt #841 AUI use & 8 direct RS232 ports $ 1870 $ 1515 2340A opt #842 ThinLan & 8 direct RS232 ports $ 1920 $ 1555 2340A opt #850 8 additional direct RS232 ports $ 1410 $ 1140 DTC48 UPGRADE-KIT ----------------- The DTC48 Upgrade kit provides the required hardware/firmware to support the new functionalities introduced from the HP OpenView DTC Manager release 10.5. This kit consists of an enhanced asynchronous card which replaces the existing one located in slot #0. As such this upgrade kit does not require any additional slot. Note that this card is HP installable. The upgraded card is left to the customer. NOTE THAT THIS UPGRADE KIT ONLY APPLIES TO DTC48 WITH A DATE CODE LESS THAN 3110 (since all the DTC48 shipped after March 26, 1991 are equiped with the new card) AND THAT NO UPGRADE IS REQUIRED FOR THE DTC16. For more information, please refer to the "Migration Guidelines" section in this hotline. ORDERING THE PRODUCT: P/N Description U.S. List price ------------------------------------------------------------ 2348A DTC48 upgrade-kit, memory $1,290 extension for the HP 2345A with datecode less than 3110. One upgrade-kit required per DTC48 ------------------------------------------------------------ THE DISCONTINUANCE OF THE HP TS8 -------------------------------- When the HP TS8 was introduced in early 1988, its objectives were to 1. help customers migrate from HP 3000 MPE V systems to HP 3000 Series 900 systems. 2. allow customers to access multiple HP systems on a same LAN as well as non-HP systems. 3. support direct CPU access to the HP-UX family via the LAN. During last year we have worked to evolve the DTC from a LAN-based mux for HP 3000 Series 900 systems to a full multi-vendor terminal server. The following steps were taken to achieve this: 1. During the summer of 1989, the DTC has been enhanced to provide access to multiple HP 3000 Series 900 systems. 2. In February 90, the DTC/3000 was enhanced with "Extended Switching" capabilities and as such has replaced the TS8 for the migration from MPE V systems. We guaranteed protection of the previous HP TS8 investment by supporting extended switching configurations in which HP TS8s and DTCs are used together. The same enhancements have also allowed the DTC/3000 to provide transparent connectivity to HP 9000 and non HP systems (through the back-to-back configuration). The supported configurations include DEC VAXes, both via the system multiplexers and the DECservers, and remote system access through the HP 233X PADs. 3. The DTC/9000 has been introduced last January to allow terminal access to multiple HP 9000 Series 800 access; shared printers and modem support have been added last August, thus removing the need for an HP TS8 in this environment. Again, compatibility between the HP TS8 and the DTC was guaranteed by supporting this shared printer and modem capabilities on both products. 4. With the availability of the DTC16 /9000, HP has created a family of scalable terminal servers which now also addresses the need for smaller portcounts in distributed environments. In summary: The needs that were addressed by the HP TS8 in the past are now all addressed by the DTC family, which is HP's strategic platform for identical local and remote end-user access. As a consequence, the HP TS8 and related products has been taken off the CPL on March 1, 1991: P/N Product Name Removed from CPL HP 2342A HP Terminal Server 8 ports March 1, 1991 HP 2350A HP Local Server Manager March 1, 1991 HP's COMMITMENT TO TS8 INVESTMENT PROTECTION --------------------------------------------- 1. TS8 purchased for HP3000 Series 900 access with switching and HP3000 MPE/V with switching: +-----+ |MPE/V| +-----+ ||||| +-----+ +-----+ +-----+ +-----+ | XL1 | | XL2 | .... | XL3 | | TS8 | +-----+ +-----+ +-----+ +-----+ | | | | ************************************************** | | | | +-----+ +-----+ | +-----+ | DTC | | DTC | | | TS8 | +-----+ +-----+ | +-----+ ||| ||| | ||||| +------------+ | Terminals | TS8s |------+ +------------+ o There is no longer a need for such combinations TS8/DTC. Existing TS8 can be re-used for connecting HP 3000 MPE/V or other systems for Back to Back connections. The DTC is always compatible with the TS8 for these back to back configurations. o In addition, the DTC provides HP3000 MPE/V access to both local and remote end-users ( remote via X.25, or via extended LANs ). Note that this is also true if a DTC and a TS8 are connected in back-to-back with an X.25 network access card installed in the DTC. 2. TS8 purchased for HP9000, HP1000 and multivendor connectivity : +-----+ +-----+ +-----+ |HP- UX| | RTE | .... |ARPA | +-----+ +-----+ +----- + | | | *********************************** | | +-----+ +-----+ | TS8 | | TS8 | +-----+ +-----+ o DTC have now to be ordered if additonal ports are required. The DTC provides Multisession/Domain Names support and more...(Printer sharing between HP systems for instance). The HP9000 systems can access TS8 and DTC printers. Both DTC and TS8 provides end-user access to the systems using the Telnet protocol. o In addition, the DTC supports X.25 connections for remote PAD access. In terms of multivendor connectivity, the DTC supports more than the non-HP systems supported by the TS8. In conclusion, whatever the TS8 environment is, the LAN environment can evolve with DTCs. This evolution protects previous TS8 investments as: o TS8 and DTC are compatible for back-to-back configurations o HP9000 DTC Device Access/ARPA software providing HP9000 access to DTC printers and other devices is also compatible with the TS8. o New DTC services ( e.g. remote back-to-back access ) are also available if TS8 are involved. NOTE ON TS8 & DTC NETWORK MANAGEMENT: ------------------------------------- When using TS8 and DTC on the same networks, two PC-based workstations are required to provide the network management functions of both TS8 and DTC: - HP OpenView DTC Manager application providing DTC management - LSM application providing TS8 management Though some applications coexistence testing on the same PC were done ( it works, but only one application can be active at a time ), HP strongly recommends to use two PCs to run these two applications. NOTE ON SOME TS8 / DTC SPECIFIC DIFFERENCES: ------------------------ ------------------- The TS8 provides some specific features mainly used with back- to-back configurations that are not today implemented in the DTC. The most significant features are: | - Escape from data-transfer string support ( "HOLD-SEQ/CHARS" | parameters ) | - Permanent connection establishment string ( "DEMAND-WAKEUP" | parameter ) | - Disconnect string ( "DISC" parameter ) | - Capability to position a back-to-back path in binary from the | management workstation ---> addressed by DTC 12.0 release | - Hardware handshake in back-to-back GND is currently investigating how some of these features could be implemented in future releases of the DTC. This hotline will be updated as soon as new information is available. Contact your Network Sales Center for more specific information. ======================================================================= /////////////////////////////////////////////// * * * D. ORDERING INFORMATION * * * /////////////////////////////////////////////// ORDERING THE DTC P/N LAN Options Asynchronous Options X.25 Options --------------------------------------------------------------- ------ DTC16 2340A Thinlan 8 direct RS232 ports RS232 access AUI configuration 6 modem RS232 ports Thicklan DTC48 2345A Thinlan 8 direct RS232 ports 1 RS232 access AUI configuration 8 direct RS422 ports 1 V35 access Thicklan 6 modem RS232 ports 1 V36 access 1 RS422 access ORDERING THE DTC16 ------------------ ============================================================== | THIN LAN | AUI (no MAU) | THICK LAN ACCESS | CONFIGURATION | CONFIGURATION (1) | CONFIGURATION --------------------------------------------------------------- 6 MODEM | 2340A, #642 | 2340A, #641 | 2340A, #640 PORTS(2)| | | | | | 8 DIRECT | 2340A, #842 | 2340A, #841 | 2340A, #840 PORTS | | | | | | 12 MODEM | 2340A, #642, | 2340A, #641, | 2340A, #640 PORTS | AND #650 | AND #650 | AND #650 | | | 6 MODEM +| 2340A, #642, | 2340A, #641, | 2340A, #640 8 DIRECT | AND #850 | AND #850 | AND #850 | | | 16 DIRECT| 2340A, #842, | 2340A, #841, | 2340A, #840 | AND #850 | AND #850 | AND #850 --------------------------------------------------------- X.25 | ADD #310 TO THE DTC16 CONFIGURATION | (HP 2343D WHEN ORDERED AFTER INITIAL DTC16 | PURCHASE) ============================================================ 8 ADDIT. | ORDER HP 2343A DIRECT | (WHEN ORDERED AFTER INITIAL DTC16 PURCHASE) --------------------------------- -------------------------- 6 ADDIT. | ORDER HP 2343C MODEM | (WHEN ORDERED AFTER INITIAL DTC16 PURCHASE) ------------------------------------------------------------ (1) To connect to EtherTwist, order in addition the EtherTwist MAU (P/N HP 28685A). (2) One modem port is needed per HP 3000 Series 900 system to do remote diagnostics. This is required when subscribing for a support contract. ORDERING THE DTC48 ------------------ ================================================================+ | THIN LAN | AUI (no MAU) | THICK LAN | ACCESS | CONFIGURATION | CONFIGURATION (1) | CONFIGURATION | -----------------------------------------------------------------+ Order | 2345A, #242 | 2345A, #241 | 2345A, #240 | and from 1 to 6 following asynchronous cards: | | | | | 8 DIRECT | 2345A, #803 | 2345A, #803 | 2345A, #803 | PORTS | | | | | | | | 6 MODEM | 2345A, #625 | 2345A, #625 | 2345A, #625 | PORTS | | | | | | | | 8 RS- 422 | 2345A, #805 | 2345A, #805 | 2345A, #805 | PORTS | | | | ----------------------------------------------------------------+ X.25 | ADD #310 ( RS-232 ), #320 ( V35 ), #330 (V36) | | or #340 ( RS-422 ) TO THE DTC48 CONFIGURATION | | (HP 2346D/E/F/G WHEN ORDERED AFTER INITIAL DTC48 | | PURCHASE) | ================================================================+ 8 ADDIT. | ORDER HP 2346A | DIRECT | (WHEN ORDERED AFTER INITIAL DTC48 PURCHASE) | ----------------------------------------------------------------+ 8 ADDIT. | ORDER HP 2346B | RS-422 | (WHEN ORDERED AFTER INITIAL DTC48 PURCHASE) | ----------------------------------------------------------------+ 6 ADDIT. | ORDER HP 2346C | MODEM | (WHEN ORDERED AFTER INITIAL DTC48 PURCHASE) | ----------------------------------------------------------------+ Note: Option #015: Set for 220v operation (1) To connect to EtherTwist, order in addition the EtherTwist MAU (P/N HP 28685A) IMPORTANT: AT LEAST ONE ASYNCHRONOUS CARD MUST BE ORDERED PER DTC48. THIS FOR INSTALLATION/SUPPORT REASONS & DUE TO ADDITIONAL MEMORY INSTALLED ON THE FIRST CARD OF THE DTC48. It is not possible to have a DTC48 with only one X.25 network access card. As written in the CPL, "From 1 to 6 asynchronous card MUST be ordered". THIS RULE IS VALID EVEN IF YOUR CUSTOMER ALREADY HAS SPARE ASYNCHRONOUS CARDS. ORDERING THE DTC/X.25 NETWORK LINK ---------------------------------- Below are ordering checklists for the DTC/X.25 links, based on whether the customer is ordering the DTC48/X.25 Network Link or the DTC16/X.25 Network Link. These checklists strictly focus on remote end-user connectivity requirements (PAD support) in PC-based environments. Please refer to the "Product Requirements" chapter for more information. Note: For customers willing to perform HP3000-to-system communication or X.25 programmatic access, the X.25 XL System Access product is required (HP 36939A). Please refer to the "DTCX25" Hotline for more information about the DTC/X.25 solution. PLEASE REFER TO THE CORPORATE PRICE LIST FOR EXACT PRICES DTC48/X.25 NETWORK LINK ORDERING CHECKLIST __________________________________________ 1. HP 2345A DTC48 (if necessary) If the DTC48/X.25 Network Access card is to be used in a DTC with a date code lower than 2851, a ROM upgrade is required. There are 2 possibilities: a) The customer doesn't want to use the multivendor features provided by the HP OpenView DTC Manager release 10.5, but ONLY the DTC as an HP3000 terminal server providing X.25 connectivity: he needs to purchase the option 001 on the add-on DTC/X.25 Network Access cards. b) The customer wants to use the new multivendor features provided since the HP OpenView DTC Manager release 10.5: he needs to purchase the "DTC48 upgrade-kit" P/N 2348A which also includes this X.25 ROM upgrade. 2. HP 2346D/E/F/or G DTC48/X.25 Network Access card and 3. HP 32054C HP OpenView Windows Workstation including connection option (ThinLAN, ThickLAN, Ethertwist), keyboard localization option and HP OpenView DTC Manager option (#201). Note: for customers using an already installed HP or non-HP supported PC, the HP OpenView DTC Manager can be ordered in a standalone manner (D2355A). DTC16/X.25 NETWORK LINK ORDERING CHECKLIST __________________________________________ 1. HP 2340A DTC16 (if necessary) and 2. HP 2340A option 310 or 2343D DTC16/X.25 Network Access card and 3. HP 32054C OpenView Windows Workstation including connection option (ThinLAN, ThickLAN, Ethertwist), keyboard localization option and HP OpenView DTC Manager option (#201). Note: for customers using an already installed HP or non-HP supported PC, the OpenView DTC Manager can be ordered in a standalone manner (D2355A). ORDERING THE TELNET SERVICES FOR THE HP 3000 SERIES 900 --------------- ---------------------------------------- The hereunder table is a summary of the Telnet Services for the HP 3000 Series 900 Product Structure. For more detailed information, we strongly recommend you to refer to the ARPA/iX Network Hotline ("ARPA/iX"). Customers requiring the Telnet services for the HP 3000 Series 900: -- ---------------------------------------------------------------- ____________________________________________________________________ | P/N Description U.S. List Price | |-- -------------------------------------------------------------- | |HP 2344A HP ARPA Telnet Express $18,000 | | opt 015 Set for 220V operation $ 0 | | opt 240 Configure for ThickLAN operation $ 465 | | (AUI and MAU provided) | | opt 241 Configure for ThickLAN operation $ 0 | | (no AUI or MAU provided) | | opt 242 Configure for ThinLAN operation $ 0 | | (BNC T-connector provided) | |------------ --------------------------------------------------- | |HP 2347A HP ARPA Telnet Access $ 6840 | | opt 001 DTC48 Upgrade Kit - provided a $ 1290 | | required memory upgrade for DTC48's | | with a datecode less than 3110. | |____________________________________________________________________| Customers requiring the Telnet and FTP services for the HP 3000 Series 900: ____________________________________________________________________ | P/N Description U.S. List Price | |-- -------------------------------------------------------------- | |HP 36955A HP ARPA/40 Services/iX | | (Includes Telnet Access card | | and FTP for the specified system) | | opt 310 For Series 920,922LX $ 7040 | | opt 315 For Series 922RX $ 8150 | | opt 320 For Series 925,925LX,922,932 $ 9670 | | opt 001 DTC48 Upgrade Kit $ 1290 | |------------ ---------------------------------------------------- | |HP 36956A HP ARPA/80 Services/iX | | (Includes Telnet Express and | | FTP for the specified system) | | opt 330 For Series 935,948 $22,375 | | opt 335 For Series 949 $24,850 | | opt 340 For Series 950,955,958,960 $28,000 | | opt 350 For Series 980 $34,400 | | opt 015 Set for 220V operation $ 0 | | opt 240 Configure for ThickLAN operation $ 465 | | (AUI and MAU provided) | | opt 241 Configure for ThickLAN operation $ 0 | | (no AUI or MAU provided) | | opt 242 Configure for ThinLAN operation $ 0 | | (BNC T-connector provided) | |------------ ---------------------------------------------------- PRODUCT REQUIREMENTS -------------------- Service | DTC16 DTC48 Network Management ---------------------|------------------------------------------------ Local End-User Access| | Single HP 3000 S 900 | 2340A 2345A included | + async cards + async cards in MPE/XL | + LAN options + LAN options FOS tape | (NMMGR, | TermDSM) | Single HP 9000 S 800 | 2340A 2345A J2120A | + async cards + async cards | + LAN options + LAN options | Multiple systems | | HP 3000 S 900 | 2340A 2345A D2355A + Access to non- | + async cards + async cards Rel 3.0 TCP/IP hosts | + LAN options + LAN options or later ("back-to-back") | | HP 3000 S 900 | 2340A 2345A D2355A + Access to non- | + async cards + async cards Rel 10.5 TCP/IP hosts | + LAN options + LAN options or later ("back-to-back") | + Memory + HP 9000 access | Extension Kit + Multivendor connect| (HP 2348A) | if DTC48 datecode | less than 3110 | Remote End-user access | HP 3000 S 900 + | 2340A 2345A D2355A HP 9000 + | + async cards + async cards Rel 10.5 Multivendor + | (minimum 1 in slot 0) or later Access to non-TCP/IP | + LAN options + LAN options hosts (back-to-back)| + X.25 card + X.25 card HBX.25 is | + Memory included in | Extension Kit the MPE/XL | (HP 2348A) if FOS for | DTC48 datecode single | less than 3110 HP 3000 S | 900 X.25 | access System-to-HP 3000 Series 900 | X.25 communications | (requires the 36939A | product on the MPE/iX| host) | | Multiple HP 3000 S900| " " D2355A | Rel 3.0 | or later | | HBX.25 is | included in the | MPE/XL FOS | for single | HP 3000 S 900 | X.25 access | | Telnet Services | 2340A 2345A D2355A for HP 3000 S 900 | + async cards + async cards Rel 10.5 | + LAN options + LAN options or later | + 2347A | + Memory | Extension Kit | (HP 2348A) | if DTC48 date code | less than 3110 ======================================================================= /////////////////////////////////////////////// * * * E. MIGRATION GUIDELINES * * * /////////////////////////////////////////////// 1. HP OpenView DTC Manager (PC-based version) When customers receive their update copy of HP OpenView DTC Manager, before it can be installed, they must ensure that they have the following software and hardware: Software Stack HP OpenView DTC Manager Release 12.1 HP OpenView Windows 4.0 MicroSoft Windows 3.1 Arpa/DOS services 2.1 DOS 3.3, 4.0 or 5.0 DTC Hardware ALL existing DTC48/9000s must have a DTC48 Upgrade-Kit installed. (HP 2348A) For the existing DTC48/3000s, the Upgrade Kit is only mandatory for using the new functionalities provided by the 10.5 and 12.0 releases. Otherwise, they will keep 6.0 functionality level (cf. matrix below) ----------------------------------------------------------------- ----- | Release Vehicle | DTC 6.0 | DTC 10.5 | DTC 12.0 | DTC12.1 | ------------------------------------------------------- ------------- | | | | | | | | --> | 6.0 -> | 6.0 -> | 6.0 | | | | | \ | \ | | | Functionality | | | \ | \ | | | Level | 6.0 | (*) \ | (*) \ | | | | | \| \| | | | | |\ |\ | | | --> | 10.5 -> | \ 12.0 -> | \ 12.1 | | | (*) | | | | ------------ --------------------------------------------------------- (*) Migration path requiring a DTC48 memory upgrade (if datecode < 3110) PC Hardware The same as for previous releases. If the customer does not have at least the above, then he/she should NOT attempt to install HP OpenView DTC Manager Release 12.1. There are two migration tools which need to be run in order that the customer be able to use, effectively, the new DTC Manager Release 12.1 (they are available since the DTC Manager release 10.5). Database Migration A program will be run automatically at the end of the installation process to upgrade the customers file and directory structure. This upgrade is needed to accomodate some of the internal changes in the configuration Database for the new functionalities of HP OpenView DTC Manager. This tool is automatic and the customer should not need to interrupt the process. The customer may need to run this tool manually if he/she restores an old back-up (prior to release 10.5). The tool can be run manually from MS DOS or within MS Windows to update old directory and file structures. The program file can be found in: C:\DTCMGR\EXE and is called CFGUPDAT.EXE this tool will use a data file called CFGUPDAT.DAT Refer to Chapter 3 in the new "DTC Manager Installation and Upgrade Guide" (Part Number D2335-90013). Map - ICON Migration It should be noted that with the release 10.5 of HP OpenView DTC Manager the icons DTC 16/9000, DTC 16/3000, DTC 48/9000 become obsolete. The reason behind obsoleting these icons is due to the convergence of the DTC, that is a DTC may no longer be tied to one system (except in Host based), yet can have access to a 3000, 9000 or a non HP system implementing TELNET/TCP/IP. In order to make the migration to the new DTC icons - DTC 16 & DTC 48 - a new menu has been developed in OVDRAW that enables the migration of customer maps. The first time the customer installs release 12.0, at the end of the installation OVDRAW will be executed automatically, thus drawing the attention of the customer to migrating his network map. To update a map the customer simply "pulls down" the update menu and clicks on "Update DTC Manager Map". The tool will scan the map and the file and directory structure to see what needs to be updated. It will automatically update all the DTC 16/48 9000s and DTC16 3000s. The DTC 48 3000s must be treated slightly differently. If a DTC 48/3000 has a Telnet Access Card configured it will be automatically migrated. If a DTC 48/3000 has a DTC48 upgrade-kit (HP 2348A) installed then it MAY be automatically migrated. The DTC 48/3000 icon will only be automatically migrated if the HP OpenView DTC Manager detects that there is a DTC48 upgrade-kit installed i.e. if the DTC has been downloaded with Release 12.0. Once the DTC Manager has this information the customer will no longer be prompted to migrate this icon as the DTC Manager will have detected that this particular DTC icon needs migrating. The customer MUST leave the icon as DTC 48/3000 IF there is no Telnet Access or memory extension installed. If not, when the Download is performed an ALARM is logged and the DTC will be unusable (note that nothing prevents the customer to migrate the icon). If the customer DOES NOT migrate a DTC48 which has a Telnet Access card or a DTC48 upgrade-kit then an event will be logged in the DTC Manager event log files stating that the DTC48 is being under used. In this case the the DTC will have Release 6.0 functionalities. (This should not happen as the Telnet Access card should normally be configured when the hardware is installed - and if it is configured then the icon migration will be automatic). How can a customer know what is installed in his DTC48s? If the DTC in question is downloaded the customer can do a "SHOW STATUS" on the CPU of the DTC this will show the following:- HP 2345A for a normal DTC - Use the DTC48/3000 icon HP 2345A WITH MEMORY EXTENSION - Use the DTC48 icon If the DTC48 is not downloaded then the customer can check the serial number of the DTC. Any DTC48 with the date code 3110 or after has automatically the memory extension installed. If the customer has run the map migration tool once and is unsure about which DTC48s contain memory extensions, he can simply download his DTC48s (by resetting them). Then run the map migration tool again. This time the migration tool will automatically migrate all the DTC48s with a memory extension and will only prompt the user for the DTC48s without a memory extension. These DTCs must be left with the DTC48/3000 icon. If the customer is still not sure, then a fail-safe method is to look at the installation tabs on the card itself (after removing the front cover). If the tabs are green then this is a memory extension board (part No. 02345-60031). If they are red then this is a traditional board. 2. HP OpenView DTC Entry-Level Manager/UX (host-based version) When customers receive their update copy of HP OpenView DTC Entry-Level Manager/UX, before it can be installed, they must ensure that they have the following software and hardware: Software Stack HP OpenView DTC Entry-Level Manager/UX Release 2.0 DTC Hardware ALL existing DTC48/9000s must have a DTC48 Upgrade-Kit installed. (HP 2348A) ------------------------------------------------------ | Release Vehicle | HB-UX 1.0 --(*)--> HB-UX 2.0 | ------------------------------------------------------ (*) Migration path requiring a DTC48 memory upgrade (if datecode < 3110) If the customer does not have at least the above, then he/she should NOT attempt to install HP OpenView DTC Entry-Level Manager/UX Release 2.0. Transparent upgrade to the Release 2.0 is provided by an embedded migration tool. ======================================================================= /////////////////////////////////////////////// * * * F. Q&A * * * /////////////////////////////////////////////// Technical Information --------------------- Q. The DTC provides a third mode of TIO interface, called "field-mode". What is the benefit? A. Today's iX TIO interface is optimized for block mode type transactions. HP's block mode type operations are not functionally compatible with the more recent window-like terminal interfaces used by the 3 & 4GL tools which we wish to support. Furthermore, only HP-type terminals could be supported. While implementing such applications using iX character mode preserves their functionality and feel, the resulting CPU overhead is intolerable. Through working directly with the 3rd party developers requests from CSY, HP adds features to iX TIO to allow the use of a third mode of TIO called "field mode." Field mode allows an application to have near the flexibility of character mode TIO without substantial performance degradation when compared to block mode TIO. Field mode functionality will be obtained by enabling the use of multiple AEOR (alternate end-of-read) and multi-byte AEOR (e.g. Escape...) characters, supressing their echo to the terminal, and utilizing an inter-byte timer to allow both read completions without AEOR and single-read transfer of multi-AEOR sequences. Required along with the application support is the enhanced support of non-HP ANSI terminals. The backspace feature is deemed critical to the proper support of these terminals. Q. The HP9000 MUX allows applications to identify and control individual ports. How does an HP9000 application identify the physical location (DTC, board, port) of a login Telnet session? Can an application directly initiate a Telnet session on a DTC port? A. With the latest DTC release, most of the applications that have been designed for Muxes can be used with the DTC without modifications through the implementation of a Mux-compatible interface. For more information on the subject, please refer to the "Product Description" section in this hotine. Q. What about performance/tuning considerations when configuring DTCs? A. Terminal I/O to HP9000 performance measurements is available in this Hotline and in Performance Hotline . They help you to position and build HP9000 configurations, with specific requirements. Q. Are the HP 9000 Series 700 supported with the DTC? A. Access to the HP 9000 Series 700 is supported when the DTC is downloaded and managed from the HP OpenView DTC Manager workstation. On the other hand, the HP OpenView DTC Entry-Level Manager/UX product is currently not supported with the HP 9000 Series 700. Q. Does the DTC provides end-users with a transparent access at connection time to either HP 3000 Series 900 systems, Telnet systems or "back-to-back" connected systems, wherever they are located? A. Yes. The choice of the protocol is totally transparent to the end-user. The DTC determines whether it has to use the Telnet/TCP/IP protocol suite or the HP 3000 Series 900 protocol. Q. What are the non-HP systems that we currently support with HP's DTC? A. DTC interoperability Matrix as of February 3rd 1992 *************************************************** This list of non-HP systems tested with the DTC Multivendor Test Guide. The Multivendor Test Guide is available from KDB using MVDTC keyword or by sending an HPDesk message to ARPAXL IOP using TNTEST as subject. Tested Non HP systems: Vendor Type OS revision Remarks SUN SUN 4 SunOS 4.1 Character mode only HP terminal emulation under evaluation at GND. DEC VAX VMS 5.3 using WIN/VX 5.1 and mux connected terminal APPLE MACTCP 1.01 using REFLECTION 1 from WALKER using BUSINESS SESSION 3.9 from TYMLABS UB ACCESS- TCP 16.3 Terminal server ONE IBM PS2 TCP using REFLECTION 1 from WALKER Testing in progress: (Please contact GND for uptodate information) =================== System ------ XYPLEX Terminal server APPLE Talk to ethernet bridge from KINETICS Tests under evaluation in field: =============================== STRATUS PC's access Known running configurations not tested by HP: ============================================= System ------ ALLIANT FX/2800 (BSD 4.3) IBM 9121 (TCP/IP 1.2.1) IBM RS6000 (AIX 3.1) IBM PS/2 (AIX PS/2 1.1) DEC VAX (ULTRIX 4.1) DEC VAX VMS with CMU-TEK 6.3 3COM Communication servers (TCP v20000 or later) PC's running NCSA Telnet 2.2 Q. It is possible to configure one IP address per DTC port. What does that bring to the customers? A. The first benefit is to provide a way of identifying and control individual ports from HP 9000 hosts (for more info, please refer to the "Product Description" section). The second benefit is to allow any Telnet source (PC or workstation) to get access to an individual DTC port, in other words to get access to any host or device currently supported in back-to-back configuration, including MPE-V, HP 9000, HP 1000, VAX systems and 2335s. Note that a Telnet access to a 2335 port will provide a Telnet/PAD capability (outgoing X.25 access for Telnet sources). The third benefit is to allow DTC back-to-back connections over IP router to be working without additional conversion hardware. With DTC release 10.5, end-user access to a system connected through a DTC back-to-back configuration over IP routers required the use of a Telnet Access Card (or a Telnet Express) on the LAN segment where the target system is located. This provided the IP@/port mapping mechanism. Q. Are bridges and routers supported between a DTC and a system? A. The DTCs are supported over HP Level 2 Bridges as well as over HP Routers used as Level 2 bridges, provided that the bridges do not loose more than 1% of the large (1500 bytes) packets. The DTC may experience problems with such configurations during downloads, uploads and X.25 system-to-system communications. The DTCs are not supported with non-HP bridges (except when explicitly stated); you will need a Net-Assure contract to cover them. Since DTC Manager release 10.5, the access to target Telnet/TCP/IP systems is supported through level 3 IP routers (either transparent or non-transparent IP routers). Note that the Telnet/iX services are mandatory for access between a DTC and an MPE/iX system through level 3 IP routers (for more information about end-user access through IP routers, please refer to the "Connectivity Matrix" in section B/ and to the DTC Management chapter of this hotline for DTC Management through IP routers). HP supports the use of the following routers: HP Routers, Cisco, Proteon, Wellfleet Q. Can the same DTC support both local and remote PAD terminal connectivity? A. Yes. A DTC48 can house up to six cards, and up to three of these can be DTC48/X.25 Network Access cards. A DTC16 can house up to two asynchronous cards and one DTC16/X.25 Network Access card. In both DTC48s and DTC16s, asynchronous and DTC/X.25 Network Access cards can be used concurrently. Q. Does the DTC/X.25 Link support SYSTEM-TO-SYSTEM communication for HP-UX systems? ( DTC/X.25 Link includes the DTC/X.25 Network Access card and the associated DTC software provided by the HP OpenView DTC Manager software) A. No. The DTC/X.25 Link supports SYSTEM-TO-SYSTEM communication for MPE/iX hosts ONLY. If the customer needs to use the Arpa/Berkeley, NS or OSI services over X.25 for HP-UX hosts in his DTC environment, 2 solutions are available according to the connectivity requirements: a) use the native X.25/9000 Link b) use an IP router over X.25 (note that the HP 9000 itself can be used as IP router from a LAN to X.25) In both cases, the customer will gain performance by separating the interactive and batch traffic by using one of the above solutions in conjunction with the DTC Pad to Telnet converter. Q. How many PAD users can a single DTC48/X.25 Network Access card support? How many can a DTC16/X.25 card support? A. The number of PAD users supported on a DTC48/X.25 Network Access card with acceptable response time depends enormously on the specific application and type of user. In HP3000 environments, HP has tested up to 60 average users and found the response times to be acceptable. More detailed information is available in the December 1989 issue of "Performance News Notes". Customers should review their requirements with a network trained SE who is familiar with this information. The number of PAD users supported on a DTC16/X.25 Network Access card is limited by by the number of virtual circuits supported. The maximum number of VCs available is 32, and the DTC16/X.25 Network Access card should provide acceptable response times even with usage approaching that limit. In HP9000 environments, the maximum number of concurrent sessions is limited by the network traffic generated by the character-mode nature of the applications (the PAD is not able to perform local echo). As an example, for a medium workload (2 characters input per second), HP has tested up to 15 sessions and found the responses times to be acceptable. (For more information about the HP9000 testing environment, please refer to the "Performance" section in this hotline). Q. Which remote terminal (PAD) applications will the DTC/X.25 Network Link support? A. The links support all character mode and VPlus block mode applications. Other applications, such as non-VPlus block mode, or binary transfer are not supported by the link, but are supported across an X.25 network using "back-to-back" HP 2335A PADs. This last configuration provides a behaviour similar to local TIO attachment and will be prefered when access to the applications described above is required. PAD users are able to perform ASCII file transfers and to use command file languages through the support of a read trigger character (DC1 in most of the implementations). In addition, a simplified type ahead (echo off) implementation is now supported with DTC release 12.1, allowing PAD users to run strategic third-party applications such as Cognos "Quick". HP is working on improving the transparency between local (pure TIO) and remote (X.25) application access. New enhancements will be provided in the next releases. Q. How transparent will be the port of MPE/V applications to be used over X.25? A. In most configurations HP customers will not experience any problem when migrating their remotely accessed applications from MPE/V to MPE/iX. However, due to a very standard abiding implementation of the CCITT X.29 recommendation, some less rigorous non-HP PADs may cause few problems. Since MPE/V HP customers may use one of these equipments, the situation has been dramatically ameliorated with the new 12.0 release: The support of non-HP PADs and terminals and the migration from DS or NS X.25 require that PAD profiles be configurable by the network manager. Users will have the choice of selecting among a set of predetermined profiles that will contain information such as: . enable/supress PAD Test . enable/suppress init profile . X.3 parameters setting . data transmission mode The profile may be chosen either by specifying a profile number in the Call User Data Field (dynamic configuration) or by associating a profile with a given incoming X.25 address in the PAD access table of the OVDTCMGR (static configuration). Important: although most of the problems experienced by the customers using non-HP PADs have been solved by these enhancements, we must inform the field that some of the problems induced by MEMOTEC PADs cannot be fixed by HP. These problems are tied up to the X.3/X.28/X.29 implementation in these PADs. For more information, please contact Michel FERACHOGLOU in the Grenoble Networks Division. Q. Is printer sharing available to PAD users? A. No. A PAD-connected printer can be configured to be accessed by several HP 3000 and/or HP 9000 systems. However a remote printer cannot be "shared" like local DTC-connected printers since print requests are not queued, thus require the printer to be available. Note that a third-party software called UniSpool can be used to share a PAD printer between several systems. Q. Are the new "Telnet Extension Utilities" supported for remote HP 9000 PAD users? A. Yes. Q. Does the DTC/X.25 Link provide outgoing PAD call capability for users willing to get access to applications on public or private X.25 networks (also known as PAD Emulation)? A. HP has recently listed a third-party product running on the MPE/iX host on top of the X.25 iX System Access product (HP 36939A). PADEMU/XL, supplied by "Hermes SoftLab" provides customers with an economical solution answering to their basic remote multivendor terminal access needs. For HP 9000 users, a PAD Emulation product is now available as part of the X.25/9000 Link product with HP-UX 8.0. For larger multivendor sites requiring similar capability with extensive connectivity and high performance, HP recommends using HP 2335A X.25/PADs connected to DTC asynchronous ports. This was made available by supporting extended switching to the HP 2335A, providing DTC users with a "PAD POOL" for outbound access. This configuration allows users to get access to block mode and single read oriented applications (such as HPEDIT or VI Unix editor) currently not supported by PADEMU/XL. Sales Information ----------------- Q. My customer bought in the past DTC ( DTC/9000 or DTC/3000 ), what does he need to get the DTC multivendor capabilities? A. Any existing DTC can provide multivendor capabilities. In order to get these new capabilities, the DTCs must be managed and controlled by an HP OpenView workstation. Installed DTC48 require one hardware upgrade (memory extension). DTC16s don't require any hardware upgrade. Q. The latest DTC release provides a solution for HP 9000 customers/VARs willing to use applications formely designed for multiplexers with the DTC through the use of the Telnet Extension utilities. What do customers need to get them ? A. Installed DTC48 require the memory extension upgrade kit. DTC16s don't require any hardware upgrade. From a software standpoint, a piece of code is required on the HP9000 host. This software is currently available through standard electronic delivery but will be bundled with the next revision of HP-UX. The Telnet Extension utilities are available when the DTC is managed from the HP OpenView DTC Manager workstation or from the HP9000 host. Q. When printer support is needed on the DTC for HP 9000 systems, do I need to order an option on the D2355A? A. No. With the availability of the "Telnet Extension Utilities", printer support is provided on the DTC for HP 9000 systems. Therefore, the HP DTC Device Access/Arpa software has been discontinued (remember that this product was orderable through a D2355A option in environments where the DTC was managed from the HP OpenView DTC Manager Workstation). Migration Information --------------------- Q. What happens if I use the HP OpenView DTC Manager release 10.5, 12.0 or 12.1 with a non upgraded DTC48 with datecode less than 3110? A. If your DTC48 is a DTC48/3000, it will operate at the level of functionality provided with the HP OpenView DTC Manager release 6.0. If your DTC48 is a DTC48/9000, it is mandatory to upgrade it as HP OpenView DTC Manager release 10.5 no longer supports DTC48/9000. Q. What happens if I use the HP OpenView DTC Entry-Level Manager/UX release 2.0 with a non upgraded DTC48 with datecode less than 3110 A. It is mandatory to upgrade it as HP OpenView DTC Entry-Level Manager/UX release 2.0 no longer support non-upgraded DTC48s. Q. Why do I need this upgrade kit ? A. With this upgrade-kit, any existing DTC48 becomes a multivendor communication server and can benefit of the new functionalities brought by the latest releases. The DTC48 has been improved as of date code 3110 to provide this memory as well as the DTC16 which is of a more recent design. This upgrade kit illustrates HP commitment to protect customer investments. Q. What is the difference between this upgrade card and the card provided as an option of the HP ARPA Telnet Access card (HP2347A)? A. There is no difference. The memory requirements are the same for the coexistence of the two protocol stacks and for the protocol conversion from Telnet to AFCP provided by the HP ARPA Telnet Access card. ======================================================================= /////////////////////////////////////////////// * * * G. SLIDES * * * /////////////////////////////////////////////// * Please refer to the TIOSTRAT hotline for strategic slides on the DTCs. ======================================================================= /////////////////////////////////////////////// * * * H. NOT YET PUBLISHED DOCUMENTS * * * /////////////////////////////////////////////// ======================================================================= /////////////////////////////////////////////// * * * I. POINTERS TO PUBLISHED INFORMATION * * * /////////////////////////////////////////////// HP Networking Communication Specification Guide (P/N 5091-1303E) * DataCommunication and Terminal Controller (DTC) Family * DTC "Product Brochure" P/N 5091-1884E (UPDATED VERSION NOW AVAILABLE) Computer News Articles * A new step toward making the DTC the clear terminal server of choice for HP-UX (June 1, 92) * DTC now surpasses competition with nailed ports (June 1, 92) * HP DTC family enriches HP and multivendor connectivity (Dec 1, 1991) * Field-mode TIO boosts performance of ISVs (Dec 1, 1991) * Announcing DTC Multivendor test package (Aug 1, 91) * New Multivendor Connectivity with HP's Family of DTCs (June 1, 91) * Revised Pricing for the DTC Family (June 1, 91) * Announcing the DTC48 Upgrade Kit (June 1, 91) * More X.25 Connectivity for the HP 9000 Systems (June 1, 91) * The DTC has been tested with Asian devices in MPE/XL and HP-UX environments (June 1, 91) * Announcing support of the DTC/9000 on HP9000 Series 300/400 (Mar 15, 91) * New rack cabinet alternatives for HP DTCs (Feb 15, 91) * Hermes SoftLab develops networking applications for HP MPE systems (January 1, 1991) * Enhanced DTC16 family for HP9000 Series 800 systems (Sept 15, 90) * Enhanced Terminal I/O solutions provide new business opportunities (Sept 15, 90) * Announcing support of HP DTC Device Access/ARPA on the DTC16/9000 (Sept 15, 90) Network Hotlines * TIOSTRAT * ARPA/XL * DTCX25 ======================================================================= /////////////////////////////////////////////// * * * J. INFORMATION ON DTC PERFORMANCE * * * /////////////////////////////////////////////// S800 Terminal I/0 Performance Planning Version 1.1 6/92 1. Introduction --------------- This article reports on the Telnet performance capacity of the DTC16 and DTC48, and the S800 system CPU consumption of DTC and MUX users. We class typical OLTP TIO workloads according to their intensity and present DTC16, DTC48, and MUX capacities for these workload classes. System CPU TIO consumption is also presented for each solution and class of workload for various HP9000 SPUs. Additionally, an appendix on printer connect guidelines is included. Please note that all references to "Telnet" in this document refer to Telnet access to the HP9000. The performance of Telnet to iX -- the Telnet/iX product -- is not discussed. To use this data for quick pre-sales-type TIO sizing, simply reference the System Capacity tables for the DTC and MUX as described in section 4. You'll have the number of TIO users supported for each measured SPU. Assume that both the DTC16 and the MUX can support full capacity usage. To have more precise TIO capacity planning specifications, section 4 outlines how to evaluate specific customer requirements and how to use the DTC and System Capacity tables to get all the data required. The measures were taken using HP-UX 8.0 and DTC 10.5 (PC-based management). These figures will therefore apply to all subsequent DTC releases, including release 12.1, which allows host-managed DTCs to attain the same performance levels as PC-managed DTCs. The DTC software allows the TCP protocol behavior to be customized for various network configurations and traffic levels. The performance levels presented in this report may only be obtained by using the default TCP behavior set (Set 1) or the moderate and long delay sets (Set 2 and Set 3). WARNING: The S800 CPU utilization data presented in this article represents only Terminal I/O and its related costs in the operating system and networking software. The article is intended to allow TIO capacity planning and is not sufficient for global system capacity planning. 2. Executive Summary -------------------- Background: The TIO workloads measured represent three classes of dedicated OLTP usage and reflect the high usage levels of these applications. The "Medium" workload in our classification represents a load that will be typical for most intense applications. The number of users concurrently active on a given system seldom exceeds 50% of the total user group. Allowing some margin, we would expect the DTC to have 50-75% of its ports concurrently active; in other words, a port activity rate of 50-75%. Results: The DTC16 is capable of supporting 100% port activity for the full range of user workloads tested and so can be recommended without regard to capacity limitations over this range. The DTC48 is capable of supporting 33-75% port activity for user workloads varying from Heavy to Light. Thus the DTC48 is an appropriate choice for moderate I/O rates under typical configurations. (Note that this port activity figure does not apply to MPE/iX connections using the ADCP/AFCP protocols. The DTC48 supports 100% port activity for MPE/iX connections.) The S800 system CPU consumption of Telnet connections is significantly higher than for MUX connections, but remains in a range that allows the support of the maximum configurations specified per SPU without exceeding an acceptable level of CPU utilization. *The DTC's standard Telnet implementation has been optimized to consume less host CPU per user than typical Telnet terminal servers. Our measurements have shown up to a 15% host CPU overhead reduction per DTC connection compared to 3rd party Telnet server connections (for Medium and Heavy loads). We estimate that the DTC48 can support up to 20 concurrently active LaserJet III or equivalent printers. The DTC16 is limited to 16 printers. We continue to work toward improving DTC and S800 performance via optimizing both the underlying protocols and their implementations. Planning underway for 1992/93 includes significant gains in DTC capacity, system overhead reduction, and further performance gains versus 3rd party servers. 3. The Right Solution -------------------- ** Choose between the DTC and the MUX based on the following criteria: DTC: Performance, Connectivity, & Flexibility In Multi-System & Networked Environments o High capacity server o Multi-system/multi-vendor connectivity o X.25 PAD access o iX connectivity & X.25 networking o High port count support; easy expansion o Distributed cabling scheme MUX: Price/Performance For Stand-Alone Environments o Low price per port o Low CPU usage per user o Simple configuration management ** Choose between the DTC16 & DTC48 based on the following criteria: DTC16: Telnet & MPE/iX Performance Capacity & Distributed Environment o Heavy workloads o All ports simultaneously active o Simultaneous MPE/iX and Telnet connections DTC48: Increased iX Connectivity & Greater X.25 Capacity o 100% active ports capability for MPE/iX connections o Average Telnet workloads and active ports o High X.25 line speeds and # VCs o Simultaneous MPE/XL and Telnet connections o Simultaneous Telnet/XL connections o Predominance of MPE/XL connections ** DON'T choose a 3rd party terminal server based on performance: -- ------------------------------------------------------------ Realistic workload measurements show that the DTC16 is capable of handling 100% port activity in all cases measured and that the DTC48 is capable of handling port activity and workloads in the normal range. Telnet terminal server performance is often measured on the basis of raw throughput. While this is a valid measurement to ascertain file transfer capacities, it does little to characterize the server's performance under realistic usage. This report demonstrates that the DTC attains the performance and capacity levels required by the vast majority of OLTP applications. Competitive measurements show as much as a 15% lower host CPU utilization per user with the DTC. Only so much protocol optimization can be done while remaining within the ARPA standards. All Telnet terminal servers face the same basic constraints and require equivalent host CPU resources. However, we've succeeded in optimizing the LAN protocol interactions for Medium and Heavy workloads. Our competitive studies have shown as much as a 15% system CPU cost reduction per user when compared with other Telnet servers under these workloads. 4. How To Use This Report For Capacity Planning ---------------------- ------------------------- Generally, you'll want to start with your customers expectations and requirements for several important TIO parameters. The appendices of this article explain these parameters and give recommendations for each one. Lacking specific customer data, use the recommendations below: o TIO Workload: Medium o Echo Response Time: Average < 100 milliseconds o Ratio Of Active/Total Users For SPU: 50% Active o Ratio Of Active/Total Users Per DTC16: 100% Active o Ratio Of Active/Total Users Per DTC48: 50% Active o System CPU% Allocated To TIO: 30% To know the number of DTC users supported for a particular SPU simply reference the System Capacity table in section 7. Locate the SPU and look under the User Connect column for Medium workloads. If there are two numbers, use the lesser one, as it represents the default choice of 50% user activity for the SPU. The number of MUX users is similarly found using the table in section 8. The DTC Capacity table (section 5) and the System Capacity tables give you all the information you need to do TIO capacity planning based on your own customer's requirements. You may vary the above set of TIO parameters in any way that you wish. The tables will tell you how many users can be supported per DTC and how many users can be supported per SPU for both the DTC and the MUX. See the appendices of this article for detailed definitions of these parameters. Printer connect guidelines may be found in appendix A. 5. DTC Telnet Capacity ---------------------- Maximum Active Users Per DTC Heavy Medium Light ----- ------ ----- DTC16 16 16 16 DTC48 16 28 36 The capacity ratings are derived by determining the maximum number of active ports that can be supported before the average echo response time exceeds 100 milliseconds (MS). This is the industry-accepted threshold beyond which users may begin to feel that the character echo is not instantaneous. Of course, a 100 MS average does mean that some responses exceed 100 MS. Although internal tests have suggested the true perception threshold may actually be in the 120 MS range, you may wish to be more conservative in your capacity planning if guaranteed instantaneous echo response times are required by your customer. From the table we can see that the DTC16 is capable of 100% port activity regardless of workload. The DTC48, however, is more suited toward Medium to Light Telnet workloads for which the port activity rate is 75% or less. As explained in the appendix, these capacity figures must be interpreted with actual customer needs in mind. Customers will not typically require greater than a 50-75% port activity rate over a range of users as large as 48, and will not exceed a Medium workload level for most application usages. The DTC48 can therefore be recommended for a wide range of customers. The DTC48 may also be used in cases where the DTC16 limits on X.25 VCs (32) or X.25 line speed (19.2 KBPS) would inhibit a desired PADSup/Telnet configuration. When both HP-UX and MPE/iX connectivity are desired, the DTC48 offers the above-mentioned X.25 capacity advantages for use in iX communication plus the possibility of simultaneous Telnet/iX connectivity. Remember that due to the low performance cost of direct iX sessions, the DTC48 can support 100% port activity to MPE/iX systems with power to spare. 6. MUX Capacity --------------- The various CIO and NIO MUX products are all capable of supporting 100% port activity for all workloads tested. 7. System Capacity - DTC Connections --------------------------------- --- User Connection Guidelines CPU Utilization Heavy TIO Medium TIO Light TIO Max DTC | CPU% Per Active User SPU Workload Workload Workload Physical | Heavy Medium Light | 827 162-243 222-333 368 368 | .37% .27% .15% | 850 62-93 86-129 140-210 288 | .96% .70% .43% | 855 110-165 146-219 240-360 384 | .55% .41% .25% | 870/100 286-429 400-600 600-768 768 | .21% .15% .10% Where: o 30% of the CPU is assumed to be available for TIO processing. o The Connect Guidelines range is based on the assumption that from 50% (lower figure) to 33% (higher figure) of total SPU users are concurrently active. The above table allows you to estimate the number of users which can be connected to an SPU based on our definitions of TIO workloads, user activity ratio, and CPU% available for TIO processing. Alternatively, you may use the CPU% Per Active User figure and your own appropriate activity ratio and TIO CPU allocation to do customized capacity planning. The figures presented are valid only for DTC connections. While remaining within the ARPA standards for Telnet/TCP/IP, the DTC has been optimized to reduce communication protocol overhead. Host- to-Host Telnet sessions and non-DTC terminal server sessions will have a higher CPU utilization rate per user for Medium and Heavy TIO workloads. Although time constraints have prevented measurements on additional SPUs, certain guidelines can be given. The S837/847/857 will have equivalent or greater performance than the S827 due to their larger cache sizes. The 860 will have equivalent or greater performance than the S855 again due to increased cache size. 8. System Capacity - MUX Connections --------------------------------- --- User Connection Guidelines CPU Utilization Heavy TIO Medium TIO Light TIO Max MUX | CPU% Per Active User SPU Workload Workload Workload Physical | Heavy Medium Light | 827 104 104 104 104 | .13% .09% .07% | 855 278-400 361-400 400 400 | .2% .15% .11% | 870/100 600 600 600 600 | .09% .07% .05% Where: o 30% of the CPU is assumed to be available for TIO processing. o The Connect Guidelines range is based on the assumption that from 50% (lower figure) to 33% (higher figure) of total SPU users are concurrently active. o Figures include MUX polling overhead per active or inactive user (16 port MUXs): S827: .01%, S855: .016%, S870: .007%. The above table allows you to estimate the number of users which can be connected to an SPU based on our definitions of TIO workloads, user activity ratio, and CPU% available for TIO processing. Alternatively, you may use the CPU% Per Active User figure and your own appropriate activity ratio and TIO CPU allocation to do customized capacity planning. Appendix A. Printer Connect Guidelines ------------------------------ --------- Though no specific printer measurements were taken for this report, we are able to offer some DTC printer connect guidelines which will be of aid in DTC capacity planning. The LaserJet III/IIID for example, prints at a rate of 8 pages per minute. We estimate that 20 such printers could be concurrently active on the DTC48. (The DTC16 is limited to 16.) Using this information in conjunction with the DTC Capacity Table, we can estimate the DTC capacity for mixed Telnet/printer configurations. We recommend that an active printer be considered as an active Heavy user when mixing users and printers. For example, 8 active printers on the DTC48 would allow for approximately 8 Heavy, 14 Medium, or 18 Light concurrently active Telnet users. It must be stressed that these estimates are NOT the results of specific measures and should be used with some caution. Appendix B. TIO Workload Classification ----------------------------- ----------- To simplify the analysis of customer TIO workloads, we have classified them into three categories based on their intensity in characters per second (CPS). Heavy: Characterizes high intensity TIO OLTP transactions with heavy data entry and little CPU processing delay or inter-transaction idle time. These are "heads-down" data entryapplications typically using forms and pop-up windows. Overall I/O Rate: 4 CPS Input & 96 CPS Output per active user. Medium: Characterizes relatively heavy TIO workloads which are less intensive over time than those of the Heavy category. This may be due to factors such as longer inter-transaction idle time or CPU processing delays. While the burst typing speeds of these workloads are equal to the Heavy category, inter-transaction delays of as short as 15 seconds result in an average I/O rate lower that that of the Heavy category. Thus, the majority of data entry applications will fall into this category. Overall I/O Rate: 2 CPS Input & 64 CPS Output per active user. Light: Characterizes usage ranging downward from the non-intensive but constant TIO loads of data base (DB) look-up type applications to the light usage loads of timeshare users. Overall I/O Rate: 1 CPS Input & 32 Output ranging down to .1 CPS Input & 10 CPS Output per active user. These classifications represent active OLTP users. "Delays" such as think time, screen reading time, CPU processing and DB access delay are taken into account, though extended idle periods are not. The I/O CPS estimations are not meant to be peak levels. Higher I/O levels will certainly occur, but overall rates are lower because of the above- mentioned delays and the effects of averaging over users and time. It must be noted that the applications of concern tend to be TIO- intensive by their nature. This classification therefore tends to be weighted toward the high end. Thus a "Light" OLTP user is assumed to type an average of 1 CPS constantly; "Medium" will be typical for most intense OLTP applications; and "Heavy" levels will be exceptional. Understanding and estimating a customer's TIO workload is key to estimating performance. Note that the above classifications are for TIO workloads and do NOT necessarily correspond to overall application CPU consumption. For example, software development and DB inventory applications typically generate light TIO and heavy CPU loads. Dedicated DB entry applications on a non-relational DB may generate heavy TIO and only medium CPU loads. Appendix C. TIO Guidelines --------------------------- It is useful to consider several guidelines concerning TIO activity in addition to the workload classifications above. Active/Inactive Ratio For SPU Users Is 50/50 Or Less: The workloads characterize classes of active users, but performance must not be estimated with the assumption that users are constantly "active" in the sense of interacting with the system via their terminals. Our investigations have shown that no more than 50% of total system users are typically active, and that often the level is as low as 25%. Active Users For Terminals Servers Will Vary Greatly: Of course, usage will vary with applications and types of users, and while the overall system activity rate may never exceed 50%, a given DTC or MUX card may well experience activity rates much greater or less than 50%. The overall averaging effect comes into play as the number of I/O ports increases. Thus the 50-75% port activity rate supported by the DTC48 makes it a good choice for Medium and Light workloads under normal port activity conditions. These activity ratios should be kept in mind when reviewing the DTC Capacity and System Capacity tables. Character-Mode Affects Both SPU And Terminal Server Performance: UNIX applications typically interact with the terminal on a character by character basis. The advantage of character-mode is its flexibility and "real-time" feel. Unfortunately, character-mode TIO via the Telnet protocol is relatively costly in both terminal server and System CPU resources since each character typed and its echo must be exchanged over the LAN. The net result is a degradation in DTC capacity relative to MPE/XL connections and a degradation in S800 CPU capacity relative to MUX-based connections. CPU% Dedicated To OLTP TIO Ranges UP TO 30%: It is important to note that the CPU consumption estimates used in the System Capacity table represent only TIO and associated OS requirements; no application needs are included. We estimate that a reasonable OLTP TIO CPU allocation will be approximately 30% although the amount required will vary with customer requirements. Echo Response Time Should Average < 100 MS: The key determinant of customer performance satisfaction for UNIX TIO is echo response time. Studies have shown that an echo delay of less than 100 milliseconds is imperceptible. We therefore evaluate the DTC and MUX capacities in terms of the number of ports that can be supported for a given workload before the echo response time average begins to exceed 100 MS. Of course, a 100 MS average does mean that some responses exceed 100 MS. Although internal tests have suggested the true perception threshold may actually be in the 120 MS range, you may wish to be more conservative in your capacity planning if guaranteed echo response times are required by your customer. =======================================================================